Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[#5330] Make odo build-images return an error if no Image component found in Devfile #5608

Conversation

rm3l
Copy link
Member

@rm3l rm3l commented Mar 30, 2022

What type of PR is this:
/kind bug

What does this PR do / why we need it:
See #5330 for more context.

Which issue(s) this PR fixes:
Fixes #5330

PR acceptance criteria:

  • Unit test

  • Integration test

  • Documentation

How to test changes / Special notes to the reviewer:
When running odo build-images with a Devfile that has no Image component in it, the command should not succeed and should output an error message on the standard error instead, like so:

asoro in work-laptop in /tmp/no-image-in-devfile on ☁️   
❯ odo build-images            
 ✗  no component with type "Image" found in Devfile

@netlify
Copy link

netlify bot commented Mar 30, 2022

Deploy Preview for odo-docusaurus-preview canceled.

Name Link
🔨 Latest commit de29eb3
🔍 Latest deploy log https://app.netlify.com/sites/odo-docusaurus-preview/deploys/62447d21212ab000087a0e8d

@openshift-ci openshift-ci bot added the kind/bug Categorizes issue or PR as related to a bug. label Mar 30, 2022
@odo-robot
Copy link

odo-robot bot commented Mar 30, 2022

Unit Tests on commit 5094aa7 finished successfully.
View logs: TXT HTML

@rm3l rm3l force-pushed the 5330-build-images-fails-silently-if-no-images-found branch from 973b3d9 to 03bfa2c Compare March 30, 2022 15:43
@odo-robot
Copy link

odo-robot bot commented Mar 30, 2022

Kubernetes Tests on commit 5094aa7 finished successfully.
View logs: TXT HTML

@odo-robot
Copy link

odo-robot bot commented Mar 30, 2022

Validate Tests on commit 5094aa7 finished successfully.
View logs: TXT HTML

@rm3l rm3l force-pushed the 5330-build-images-fails-silently-if-no-images-found branch from 03bfa2c to de29eb3 Compare March 30, 2022 15:54
@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@odo-robot
Copy link

odo-robot bot commented Mar 30, 2022

OpenShift Tests on commit 5094aa7 finished with errors.
View logs: TXT HTML

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. Required by Prow. label Mar 30, 2022
@valaparthvi
Copy link
Contributor

/approve

@openshift-ci
Copy link

openshift-ci bot commented Mar 30, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: valaparthvi

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. Required by Prow. label Mar 30, 2022
@valaparthvi
Copy link
Contributor

@rm3l Feel free to override prow test if it fails. IBM tests pass, so we're good to go.

@openshift-merge-robot openshift-merge-robot merged commit 293b6b2 into redhat-developer:main Mar 30, 2022
@rm3l rm3l deleted the 5330-build-images-fails-silently-if-no-images-found branch March 30, 2022 19:37
cdrage pushed a commit to cdrage/odo that referenced this pull request Aug 31, 2022
… Image component found in Devfile (redhat-developer#5608)

* Add test highlighting the issue

* Make `odo build-images` return an error if no Image component found

As reported in redhat-developer#5330, this makes more sense rather than exiting silently.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. Required by Prow. kind/bug Categorizes issue or PR as related to a bug. lgtm Indicates that a PR is ready to be merged. Required by Prow.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

build-images fails silently if no images found
3 participants